Managing Web Gateway |
|
The Web gateway is the point of contact between the current application environment and the external applications. It received HTTP requests which contain SOAP messages and forwards these to a Service Container. When a SOAP message is received the Web gateway will route the message to a specific Service Group. After the SOAP message is handled the response is send back to the caller. For information on the Web gateway and its applications, refer to Web Gateway.
The Web gateway receives a number of requests. There is statistical information that is available to understand the performance of the Web gateway. You can monitor the Web gateway using the Monitor Web Gateway tool.
Configuring Web Gateway
While installing Process Platform, you can configure the Web gateway on Apache, IIS or TomEE. This means that on every Process Platform instance there must be a web server available. For information on configuring the Web gateway on either IIS or Apache after installation of Process Platform, refer to Configuring Web Gateway on a Web Server.
When ever a request is sent to the Web gateway, the Web gateway forwards it to the appropriate service group. The client which sent the request would be waiting for the response from the Web gateway. If for some reason the gateway does not receive a response, it has to inform the client. A time has to be set so that the gateway does not wait forever to receive the response. For more information on configuring the Web gateway time-out, refer to Configuring Gateway Time-out.
SOAP requests are XML code. When these requests are not properly formatted, the application cannot work with the request and the processing of the request fails. To avoid the time spent in processing a ill-formatted request, Process Platform provides a mechanism to validate the SOAP requests and responses at the gateway itself before they are processed by service containers. SOAP requests coming in into the Web gateway can be validated to ensure that they follow the SOAP 1.1 protocol. Similarly the payload, that is part of the SOAP request excluding the SOAP protocol, in the SOAP request too can be validated to ensure that it follows WSDL Web service operation standards.
Apart from configuring Web Server, managing Web Gateway includes the following tasks:
- Enabling Payload Validation at Gateway (Deprecated)
- Enabling SOAP Validation at Gateway (Deprecated)
- Enabling SOAP Protocol Validation at Gateway
- Enabling Request Protocol Validation at Gateway
- Enabling Response Protocol Validation at Gateway
Testing Web Gateway
You may also want to test the performance of Web gateway by sending it multiple requests. To do this, Process Platform provides the Web Gateway testing tool.
Web gateway can also be used for resolving SAML artifacts with user credentials within Process Platform. For information on SAML artifacts, refer to Using SAML Artifacts Between Browser and Web Server. If you wish to configure the Web gateway with security options, refer to Managing Web Gateway with Secuirty Options.